Alerts and Approvals Summary

This is a summary of the types of approval alerts generated by Triaster Server. It offers information including:

  • The condition under which an alert is sent
  • Enabling an alert
  • The recipients of an alert
  • Records of an alert having been sent
Alert Comments
Approvals Required
  • Approval status of a map isn't 'Approved' or 'Approval Not Needed'.
  • Sent from Prelive site by convention.

    • Settings/PublicationSettings/Library/Site/SendApprovalOverdueAlerts

  • Generated at the end of a publication.
  • Sent to map's approver, e.g. 'Content Approver'.
  • Alert e-mail logged in the Publication Server service log.

    Triaster\TriasterServer2011\Logs\Services\PublicationServerLog <Date>.txt

  • Recorded in 'AlertsSent.xml': Triaster\TriasterServer2011\Alerts\AlertsSent.xml

    <Map Name="/processlibraries 2011/process library/prelive/html/map to approve - 1.map page-1.html">

    <Alerttype="ApprovalsRequired" approvertype="contentapprover">

    <Datesent>19/03/2014 15:29:34</Datesent>

    </Alert>

    </Map>

  • Record deleted from 'AlertsSent.xml' when map approved.
Approvals Overdue
  • Map hasn't been approved ('Approval Status' is not 'Approved' or 'Approval Not Needed').
  • Overdue interval exceeded since sending of Approvals Required alert (7 days by default).

    Settings/PublicationSettings/Library/Site/ApprovalsOverdueDays

  • Sent from Prelive site by convention.

    Settings/PublicationSettings/Library/Site/SendApprovalOverdueAlerts

  • Generated by the Alert Server service.
  • Sent to map's approver, e.g. 'Content Approver'.
  • Recorded in 'AlertsSent.xml':

    Triaster\TriasterServer2011\Alerts\AlertsSent.xml

    <Map Name="/processlibraries 2011/process library/prelive/html/map to approve - 1.map page-1.html">

    <Alert type="Approval" approvertype="contentapprover">

    <Datesent>19/03/2014 15:29:34</Datesent>

    </Alert>

    </Map>
Approved Maps
  • Map has been approved through the Approvals webpage.
  • Sent from Prelive site by convention.

    • Settings/PublicationSettings/Library/Site/SendApprovalOverdueAlerts

  • Generated from a 'mini/silent publish' triggered automatically when a map is approved, logged in:

    Triaster\TriasterServer2011\Logs\SilentPublish

  • Sent to map's 'Author'; can be sent to approver if requested (yes, by default).
  • Alert e-mail logged in Browser Toolkit Common Tools log.

    Triaster\TriasterServer2011\Logs\Browser Toolkit\ToolsCommonLog <Date>.txt

  • Recorded in 'AlertsSent.xml':

    Triaster\TriasterServer2011\Alerts\AlertsSent.xml

    <Map Name="/processlibraries 2011/process library/prelive/html/map to approve - 1.map page-1.html">

    </Map>
Maps Needing Rework
  • Map has been tagged for rework through the Approvals webpage.
  • Sent from Prelive site by convention.

    Settings/PublicationSettings/Library/Site/SendApprovalOverdueAlerts

  • Generated from a 'mini/silent publish' triggered automatically when a map is approved, logged in:

    Triaster\TriasterServer2011\Logs\SilentPublish

  • Sent to map's 'Author'.
  • Alert e-mail logged in Browser Toolkit Common Tools log.

    Triaster\TriasterServer2011\Logs\Browser Toolkit\ToolsCommonLog <Date>.txt

  • Recorded in 'AlertsSent.xml':

    Triaster\TriasterServer2011\Alerts\AlertsSent.xml

    <Map Name="/processlibraries 2011/process library/prelive/html/map to approve - 1.map page-1.html">

    </Map>
What's Changed
  • Map has 'Change Description' set.
  • Sent from Live site by convention.

    • Settings/PublicationSettings/Library/Site/SendWhatsChangedAlerts

  • Generated at the end of a publication.
  • Sent to e-mail address(es) associated with map 'Function'.
  • Alert e-mail logged in the Publication Server service log.

    Triaster\TriasterServer2011\Logs\Services\PublicationServerLog <Date>.txt

  • Recorded in 'AlertsSent.xml' to prevent resending of alert:

    <Map Name="/processlibraries 2011/process library/live/html/sample maps.map page-1.html">

    <Alert type="Changed">

    <Text>Some changes</Text>

    <ChangeDate>

    </ChangeDate>

    </Alert>

    </Map>
Review Due Notice
  • Sent a number of days prior to the 'Next Review Date', 30,14,7, by default, but configurable.

    Settings/PublicationSettings/Library/Site/ReviewReminderDays

  • Sent from Live site by convention.

    Settings/PublicationSettings/Library/Site/ReviewReminderAlert

  • Generated by the Alert Server service.
  • Sent to approver identified in map's 'Reviewer Name'.
  • Alert e-mail logged in the Alert Server service log.

    Triaster\TriasterServer2011\Services\AlertServerProcessLog <Date>.txt

  • Recorded in 'AlertsSent.xml':

    Triaster\TriasterServer2011\Alerts\AlertsSent.xml

    <Map Name="/processlibraries 2011/triaster sample library/live/html/map for review.map page-1.html">

    <Alert type="Revision">

    <Datesent>20/03/2014 12:52:39</Datesent>

    </Alert>

    </Map>
Reviews Overdue Reminder
  • Sent immediately after the 'Next Review Date', and then at intervals a number of days after - 7 by default.

    Settings/AlertServer/DefaultFrequency

  • Number of days can be overridden, determined by a map (Node) property, Prop.REVISIONALERTFREQ, typically captioned 'Frequency (days) of revision due alerts'.
  • Sent from Live site by convention.

    Settings/PublicationSettings/Library/Site/ReviewOverdueAlert

  • Generated by the Alert Server service.
  • Sent to approver identified in map's 'Reviewer Name'.
  • Alert e-mail logged in the Alert Server service log.

    Triaster\TriasterServer2011\Services\AlertServerProcessLog <Date>.txt

  • Recorded in 'AlertsSent.xml':

    Triaster\TriasterServer2011\Alerts\AlertsSent.xml

    <Map Name="/processlibraries 2011/triaster sample library/live/html/map for review.map page-1.html">

    <Alert type="Revision">

    <Datesent>20/11/2014 14:36:25l</Datesent>

    </Alert>

    </Map>
Last Reviewed: 23/1/2019